home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The World of Computer Software
/
The World of Computer Software.iso
/
zyrion.zip
/
ZYRION.DOC
< prev
next >
Wrap
Text File
|
1992-10-01
|
59KB
|
1,256 lines
Draft-100192
ZyRion Premium Driver
ZyRion Professional Protocol Drive Engine Module
ZyRion (Tm), Version 2.45.1.0 Wide Beta "Pß"
Pß Public Beta
(C)opyrighted by Frans Lupschen
ZyRion (C)opyrighted by Frans Lupschen
Copyright 1989,90,91,92,93
By International Communication Research [ICR ]
Part from
ProToSoFt (Communications Research) Holland
Abarated DFC Check (Tm) MatrixSoft Holland ; ALL RIGHTS RESERVED
The Oasys Project, Communication Software Research
ZyRion Designed and Programed by:
Frans Lupschen
ZYRION DC-WORD
--------------
First of all there a many protocols, I know that, Why ZyRion?
I think that you would say its the speed again, well if that was all then
ZyRion would not be so special so as it is now.
But lets talk first about speed and modems in general.
Error-correcting modems are capable of transferring data to and from
your computer at speeds far in excess of the rate at which data travels
across the phone line. The speed at which data is transferred across
the phone line is generally the speed you should be most concerned
with. Many advertisements have been sufficiently unscrupulous to
advertise the speed at which data is transferred between your modem and
your computer as being the speed of the modem.
The serial port on your computer adds one start bit and one stop bit to
each character transferred to or from your computer, using 10 bits to
transmit every 8 bit character, consuming 2 bits for overhead on each
character transferred. Error correcting protocols provide a method of
reducing this overhead when sending data across the phone line.
If all overhead could be removed, 2400 bits per second with 8 bits per
character would yield 300 characters per second; 2400 divided by 8 is
300. 9600 bits per second would yield 1200 characters per second. 14400
bits per second would yield 1800 characters per second.
The serial port on your computer still requires the additional start
and stop bits, so the serial port must operate at a faster speed than
the DCE(carrier) speed across the phone line, if it is to avoid
becoming the bottleneck of the operation. RS232(CCITT V.24) defines
only certain port speeds, such as 2400bps, 4800bps, 9600bps and
19200bps, as standard speeds for such communication, so the next higher
officially sanctioned port speed is likely to be considerably faster
than the DCE(carrier) speed.
Both MNP4 and LAP-M(V.42) provide reductions in overhead below the 2
bits per character used for 8N1 asynchronous transmission. The amount
of overhead for both MNP4 and LAP-M varies between implementations,
with good MNP4 implementations achieving about 5 1/4 percent and good
LAP-M implementations achieving about 5 3/4 percent. for which one
would multiply the figures without overhead, such as 300cps for
2400bps, by 0.9475 and by 0.9425, respectively.
The Hayes Ultra has been observed to provide about 5 3/4 percent
overhead for LAP-M and about 13 percent overhead for MNP4. For the
Hayes Ultra, one would multiply the figures without overhead, such as
1200cps for 9600bps, by 0.9425 for LAP-M and by 0.87 for MNP4. The USR
Dual Standard has been observed to provide about 7 4/5 percent overhead
for LAP-M and about 5 3/4 percent overhead for MNP4 in symmetric modes.
For the USR Dual Standard in a symmetric mode, one would multiply the
figures without overhead, such as 1200cps for 9600bps by 0.922 for
LAP-M and by 0.9425 for MNP4. The USR Dual Standard has been observed
to provide and about 6 4/5 percent overhead for V.42bis and about 5 4/5
percent overhead for MNP4 in HST assymetric mode. In assymmetric HST
modes, one would multiply the figures without overhead, such as 1800cps
for 14400bps, by 0.932 for V.42bis and by 0.942 for MNP4.
ZyRion without DFC-DC64 adds about 2 1/2 percent overhead. ZyRion
DFC-DC64 adds about 4/5 percent overhead. For ZyRion throughput,
multiply each of the cps(characters per second) values by 0.975. For
ZyRion DFC-[2048] throughput, multiply each of the cps(characters per
second) values by 0.992. For example, with ZyRion DFC-[2048] and a USR
HST Courier or Dual Standard in assymmetric mode at 14400bps using
MNP4, one should expect 1800x0.942x0.992=1682cps. Clearly, the room for
improvement in efficiencies in implementations of MNP4 and LAP-M is
much greater than the room for improvement in the efficiency of ZyRion
DFC-DC.
I got a lot requests to make ZyRion Bidirectional, ideas to release a -
ZyRion Level-2 "Bidirectional" was the next project, but I freezed it.
Because Bidirectional transfers are not that good from the point of view
in data streaming DFC(Tm), it would not improve ZyRion's speed at all.
ZyRion in one direction will be faster then Bidirectional, the structure
from DFC is assymmetric, so maybe later if I find a better way to do so
but for now I'll stick to my DFC method and NOT to NFC.
NFC has the same structure as DFC but it was "NON-STREAMING" so I dropped.
About DC Signature and BS Mode "New added"
-----------------------------------------
If ZyRion was Bidirectional then the efficiency of ZyRion would be nill
still faster then the known Bidirectional protocols, but the reliable
point of view would be bad, all Bidirectional are NOT that good as a
one direction streamed protocol (ZModem) for example. if we talking -
about fast corrections and a stable throughput. but ZyRion uses a back
stream channel, IF the receiver request so, IF not ZyRion will flow only
in one direction, the backstream channel is for fast error correction and
CRC based calculated results for file compare, Virus MTE compiled encryp-
ted situations. this makes ZyRion special already because it can check the
data for MTE or other infections "added codes" after the data subpacket -
was received, IF bad "Signature Pulse=FFFF" then ZyRion will abort, for -
security reasons, I have added this to this Version! Versions before this
one don't have it!!!
For compressed files such as ARC,ARJ,LZH,PAK,ZIP and ZOO, there is no
further compression the modem can provide, and these figures represent
the best possible throughput with the most noise-free phone line.
Transfer rates for compressed files which are greater than those
provided by these figures generally indicate a lack of accuracy in
timing the transfer.
MNP5 is a very simpleminded data compression algorithm which Microcom
has licensed for a relatively small charge. It isn't sophisticated
enough to realize when it's doing more harm than good and can easily
reduce throughput for compressed file transfer by as much as 25%. For
modems which include MNP5, make sure that MNP5 can be disabled.
Contrary to popular misconception, the presence of MNP5 does not in any
way imply the presence of MNP4. MNP5 can be implemented in combination
with any lesser form of MNP, such as MNP1, which transfers all data in
the 8N1 asynchronous format and adds an additional 30% overhead
besides. MNP2 also transfers all data in the 8N1 asynchronous format
and adds an additional 16% overhead besides.
"Software MNP5" must necessarily use MNP1 or MNP2, since MNP3 and MNP4
use data patterns which cannot pass through the serial port of a PC.
With MNP2 but without MNP5 at 2400bps, one should expect
(2400/10)x0.84x0.975=197cps throughput for compressed files using
ZyRion without DFC-2048. An extremely well-written implementation of
MNP5, taking full advantage of the processing capabilities of your PC,
might reduce throughput for compressed file transfer by only 5 percent,
allowing MNP2 with MNP5 at 2400bps to provide
(2400/10)x0.84x0.95x0.975=186cps for compressed file transfer using
ZyRion without DFC-2048.
V.42bis, an extension to the LAP-M protocol of V.42, is an algorithm
similar in sophistication to MNP7, employing the Lempel-Ziv-Welch
compression technique. Unlike MNP5, it avoids reducing throughput when
compression would accomplish nothing. This makes V.42bis quite
attractive, although the processing capacity needed to provide
effective V.42bis compression is much more than what is needed to
provide MNP4 or LAPM. Its compression of long strings of characters can
also present quite a challenge to the control of data flow within the
modem between the data traveling over the phone line and the buffers
being used to transfer data to and from your computer in the 8N1
protocol used by its serial port.
ZyRion TCM
----------
Trellis Coded Modulation, TCM, is a method of encoding an additional
bit for each cycle of the transmission carrier and using that to avoid
and to correct errors in transmission. Without TCM, transmission of
data at rates of 7200bps or greater is very likely to encounter noise
beyond the ability its error correction capabilities. If you are
considering a modem which transfers data at rates greater than 2400bps
using a single carrier, make sure that TCM, Trellis Coded Modulation,
is being used. Trellis Coded Modulation is a part of the V.32 standard,
and USR's HST assymetric mode also employs TCM, so you only really need
to ask if you're purchasing some other form of data transmission. PEP
protocol, used by Telebit and VenTel modems, is a multi-carrier
transmission method with somewhat different requirements and
techniques.
If you DON'T CARE about your "DATA" and your security ticket to be sure
it can NOT be _manupulated_ then don't read futher, IF you care then
proceed.
After this story about ZyRion and related stuff, do you still think that
ZyRion is just another nice named protocol?, IF so then please STOP.
Erase this package, IF not then you have a first class ticket to a new
Technic called DFC DC Signature scan and BS Error corrected feature.
better then all bidirectional features because they don't have it.
FAIR PLAY BEFORE READING THIS DOC.
----------------------------------
ICR Holland hereby disclaims all warranties relating to this product,
whether expressed or implied, including without limitation any implied
warranties of merchantability or fitness for a particular purpose.
ICR Holland cannot and will not be liable for any special, incidental,
consequential, indirect or similar damages due to loss of data or any other
reason, even if ICR Holland or an authorized ICR agent has been advised of
the possibility of such damages.
In no event shall the liability for any damages ever exceed the price paid
for the license to use software, regardless of the form and/or extent of the
claim.
The user of this program bears all risk as to the quality and performance of
the software.
ZyRion is a Shareware product. As such, it is made available to the
general computing public for evaluation. Users are licensed to operate
ZyRion on their personal computers for the purpose of test and evaluation
on a trial basis for a limited trial period. It is not possible to
reasonably define any definitive limits of a fair and equitable time period
for evaluation, therefore it is left to the user's judgment and sense of
fair play as to the time required to make a decision as to its usefulness.
60 days is a reasonable time though. If the user decides the program is not
of sufficient merit to warrant purchase through registration with ICR Holland
the program should be removed from their personal computer.
Otherwise, if the program is deemed useful and is in regular use on the
user's personal computer system, registration with ICR Holland is required.
Registered users are those users that elect to pay for ZyRion and
register that payment with ICR Holland. By virtue of registration and
payment for the program, registered users are granted a license to continue
to utilize the program on their personal computer for as long as they
choose.
This license authorizes the user to use the program on any personal
computer system he or she may own so long as the program is operated on
only one computer system at a time. Site licenses for use of ZyRion on
multiple computers are available upon request at a reduced fee that is
based upon the number of single machines licensed for use.
░░░░▒▒▒▓▓▓▓▓▓▓▓▓▓▓▓██████████ REGISTRATION ███████████▓▓▓▓▓▓▓▓▓▓▓▒▒▒▒░░░░░
ZyRion is sole property of ICR Holland Shareware products. The Shareware
version, and ONLY that version, may be freely copied and transfered to
individual parties for evaluation purposes. The Shareware version, and
ONLY that version, may be posted on Bulletin Board systems (BBS) for
electronic access as long as NO FEE is charged for its distribution except
for private BBS operations that charge a regular user subscription fee.
Computer information services such as Compuserve (CIS), Genie, etc., are
authorized to post this product for subscriber access. The Shareware
version of ZyRion may NOT be distributed on diskette by any disk
distributor/vendor that charges more than $12.00 for the diskette upon
which the program and attendant files are recorded without written consent
from ICR Holland. ZyRion is a fully functional Shareware product.
Shareware is a computer program distribution/marketing method that permits
potential buyers to thoroughly try the program prior to purchase. It is
NOT free and it is not in the Public Domain. If, after evaluating the
program, you find it to be useful enough to use it on a regular basis, you
are expected to pay for it by registering with ICR Holland.
The registration fee is $15.00 and then you get the registered version,
which is NOT distributed as Shareware. Those who have registered a previous
version (prior to version 2.XX) of ZyRion may purchase ZyRion version 2.44WG
as an upgrade for $5.00. (For postage and handling of diskette or for
telephone costs.) Please be advised that I cannot accept credit card orders
for the upgrade Checks/cash only, please! You may register ZyRion by using
the included File (REGISTER.EXE)
░░░░▒▒▒▓▓▓▓▓▓▓▓▓▓▓▓██████████ HOW TO GET A KEY ███████████▓▓▓▓▓▓▓▓▓▓▓▒▒▒▒░░░░░
After your registration, and after we have received your money, you can
Download or "IF" you are a SYSOP, POLL 2:284/304, 2:285/802
to obtain a KEY File.
If you cannot call any of the distribution systems, then a diskette will be
mailed to you. The diskette will contain the latest version and your key.
If applicable, the newest documentation. Users may Log on and Download the
KEY File.
Users can CALL the systems below to obtain a KEY file after registration .
ICR Headquarters Holland operates 12 hours per day, 7 days per week.
DreamScape is ON-LINE from 19:00 Hours - 08:00 Hours CET.
Phone +31-45-256961 (SYSOP Frans Lupschen), [2:284/304.0].
ICR Distribution Holland operates 24 Hours per day, 7 days per week.
Phone +31-1883-17534 (SYSOP Dick Hoogendijk), [2:285/802.0].
Only call THESE above BBS to register your version of Zyrion, these are
the only official distribution systems that are allowed to sell you your
Zyrion key.
Users who register by mail or phone may also access the registered version
by BBS, but you MUST log on and leave a comment to the sysop to the effect
that you are a registered user and desire access.
This Shareware version of ZyRion may be freely copied and passed on to
other individual users for their evaluation.
LAST DC-WORD ABOUT THE ABOVE PAGES FROM THE AUTHOR.
Unlike snazzy menu interfaces, reliable high speed transfer protocols
take many hours of testing, often over expensive phone connections, to
develop. Two decades of communications experience and protocol testing
are distilled in ZyRion.
ZyRion is a user supported program developed and supported by Frans Lupschen,
owner of ICR Holland, Countless hours of work and expensive resources went to
develop and support ZyRion for the myriad environments users use it in.
The fact that most of the problems people encounter with ZyRion are caused by
other software, hardware problems,failure to read the supplied
documentation, or pirating has not kept users from seeking and getting help,
even if it means calling the author in the middle of another project.
Beyond this, the world of communications is constantly evolving, and it
requires a significant ongoing effort to keep ZyRion and its documentation
up to date with the current state of the art. Individuals with little
knowledge of the dynamic nature of telecommunications (or hidden agendas) have
misrepresented the frequency of enhancements to ZyRion as a sign that ZyRion is
"unstable" and unworthy of "serious consideration". If you think such sniping
is fair play, you are more than welcome to use one of the many other protocol
programs available, each of which claim to offer speed and reliability
comparable to ZyRion.
Non registered users are welcome to use ZyRion for a reasonable evaluation
period. "Reasonable" means "until you've decided whether the program is
worth $15.00." It does not mean "until some competing program gets around to
adding ZYRION or True DFC-DNC(TM)". Once you've evaluated ZyRion,ethical use
of ZyRion requires registering the copy.
ZyRion is not and never has been Public Domain. Every version of ZyRion has
included a Copyright Notice and a prohibition against sale or modification.
There is no usage counter or other Trojan Horse in ZyRion, but if you use this
program, you have a moral and ethical obligation to register it.
Paid registration enables COM3-COM8, Path Support,Batch Transfers e.c,
ZyRion DFC, and other advanced features that are present in ZWGNNN.1.ARJ
in encrypted form. The registration KEY serializes and decodes all
past and future versions of ZyRion Level-1.
You can get a fully featured upgrade of ZyRion simply by downloading a newer
version from ICR Holland, and trusted bulletin boards.
Bulletin Board Registration
Note to the wise BBS operator: be sure you understand the ZyRion restrict
command and how to use it.
Use and/or copying of ZyRion by bulletin board sysops and/or systems is
allowed according to the following conditions:
I agree to feature the OASYS files (ZRNNN.LEVEL.ARJ, OAZNNN.ARJ) for
downloading, and to announce the availability and features of ZYRION
in any bulletins, help displays, or other displays that mention
communications programs.
It is my responsibility to maintain reasonably current versions of the
OASYS files or ZYRION releases on the BBS shown above.
I understand that I am welcome to use ZyRion on my bulletin board(s) from
the time I sign and mail this document as long as I abide by the
conditions above, including featuring the above mentioned OASYS files.
I shall distribute ZyRion.exe only as part of the ZRNNN.X.ARJ EXACTLY as
provided by ICR Holland, or "zipped" without any file additions, deletions,
or modifications. If I distribute ZyRion.ARC, I shall also maintain
ZRNNN.X.ARJ in the same directory since ZyRion.ARC references files in
ZRNNN.X.ARJ.
If I see a modified ZyRion archive or parts thereof in a file or collection
of files (e.g., archive) on a bulletin board, I shall replace such files
or archive members with the contents of ZRNNN.X.ARJ exactly as provided by
ICR Holland. I shall report instances of noncompliance to ICR Holland -
hereby released as "International Communication Research."
I shall not allow any version of ZyRion to be sold, modified, patched,
hacked, disassembled, decompiled, or otherwise reverse engineered
without the prior written permission of ICR Holland.
I understand that ZyRion is not and never has been Copy Protected. I fully
understand that "ZyRion unprotect" files have no function whatsoever except
to aid and encourage the theft of ICR Holland Intellectual Property.
(For this BBS registration, a multi node bulletin board operating from a
single, common file system counts as one machine.)
The purpose of bulletin board registrations is to support and promote
ZYRION and OAZMDM by popularizing the ZyRion protocol and featuring the
ZYRION shareware files available for downloading.
░░░░▒▒▒▓▓▓▓▓▓▓▓▓▓▓▓██████████ ZyRion 2.45.1WB ███████████▓▓▓▓▓▓▓▓▓▓▓▒▒▒▒░░░░░
ZyRion is a file transfer protocol written for the "IBM" family of
computers. This protocol sends data in 2048k SubPackets Last SubPkt will
be the size of the final bytes in the file, thus the original file size
will be retained. Each block has an overhead of 6 bytes.
2048 was chosen for block size as it seems to be the optimum size for CPS
and minimal impact on efficiency if an error should occur. It also happens
to be the normal size of a Hard Drive sector, 2 times a Floppy sector and
1/2 of a oversize Hard drive sector thus improving disk read/write
efficiency.
ZyRion uses the DFC error checking system for a very high reliability of
successful transfer in rough conditions with minimal transfer overhead.
All code from this ZyRion release has been completely changed, special
changes are made in the ring and disk buffer section, and DFC calculation
routines.
==============================================================================
---> IMPORTANT <---
NOTE:: YOU'LL NEED TO SET THE "ZSE" ENVIRONMENT "SET ZSE=<PATH>".
THE PATH IS THERE WHERE ZYRION IS LOCATED!
IF FOR EXAMPLE YOUR VERSION OF ZYRION, IS IN THE DIRECTORY C:\XFER
THEN YOU'LL NEED TO SET "SET ZSE=C:\XFER, IF YOU DON'T DO THIS ZYRION
WILL _NOT_ RUN!!!!
==============================================================================
ZYRION (LEVEL-1)
ZyRion is one of only available programs that implement the DFC file
transfer protocol. ZyRion features the LEVEL-1 extensions including
DFC Abarated (TM) accelerator.
ZyRion's DFC provides advanced file management features including two
levels of Intelligent Crash Recovery ,and flexible control of selective
file transfers.
The DFC file transfer protocol provides _reliable_ file and command
transfers with complete END-TO-END data integrity between application
programs. ZyRion's 64 bit CRC protects against errors that sneak by
"error free" modems and even the most advanced networks.
FC-Abarated safeguards all data and supervisory information with effective
error detection. (XMODEM and many recently introduced protocols do not
protect vital supervisory data.)
ZyRion rapidly transfers files, particularly with modern modems,
timesharing systems, satellite relays, and packet switched networks.
ZyRion's streaming operation eliminates delays caused by
Kermit/XMODEM/YMODEM/JMODEM block acknowledgements. ZyRion eliminates
traditional protocols' PACKET LENGTH compromises between transfer
efficiency and error recovery; ZyRion's Subpacket length is the entire
DFC/Matrix/Encoded Buffered file.
User Friendliness is an important ZYRION feature.
ZyRion's AutoDownload (Automatic file Download without user intervention)
provides a level of convenience unimaginable to users of traditional
protocols.
*************************************************************************
ZyRion registration is special.
With most programs, registration only applies only to today's version.
Not ZyRion!
ZyRion registration bypasses the shareware announcement and unlocks
advanced features in all future versions of ZyRion. You don't have to pay
and pay again for new ZyRion versions. ICR Holland Demand Upgrade allows
you to download and activate future ZyRion versions without further
registration!
*************************************************************************
░░░░▒▒▒▓▓▓▓▓▓▓▓▓▓▓▓██████████ SETUP ZYRIONX ███████████▓▓▓▓▓▓▓▓▓▓▓▒▒▒▒░░░░░
Before you can proceed you need to tell ZyRion wich port(s) are supported
because ZyRion will create a "ZYRIONn.CTL" file where "n" is the port or
Communication Channel (COMX), for example, you want that ZyRion operates
on port 3 (COM3) only, then you need to type "ZYRION SETUP3".
After this ZyRion will go into his setup mode for "COM3", IF you have more
ports for ZyRion "Multi-Line" or whatsover you'll need to make for each
port a seperated ZYRIONn.CTL file, in the registered mode this will be 8
in the Unregistered Mode this will be 4, COM1 - COM4 only.
You may also use ZCR.EXE to Setup ZyRion, just type ZCR thats it!
Its special and usefull to do it this way, let me tell you why, you can do
for each port seperated :
» Define the Ringbuffer size for that port
» Define either Locked rate or NOT for that port
» Define 16550AFN special overide defaults for that port
» Define for each port "THIS" a seperated download path
» Define a DTR drop only for that port
» Define total other colors for ZyRion for that port
And so on.....
I think this will be clear by now what you as user can do in this case.
Lets look at it step by step
The directory we will use here, is a example ofcource.
First create a directory "MD ZR".
Second of all you'll need to put the next statement in your "autoexec.bat"
file, if any, otherwise create a batch file by this name, and be sure to
put it in your root directory.
ADD this statement to your "autoexec.bat" file SET ZSE=C:\ZR
Ofcource if you are using another drive then "C:" you need to change the
above line SET <DRIVE> <\ZR>.
Unpack now your ZyRion package, and put it in the ZR directory.
Now "REBOOT" your system, and go to the ZR directory, now type
C:>\ZR>ZYRION SETUPn <Cr>
You will see now this screen, the key will NOT be found if you have none,
but just proceed, type "y" or just press return.
Just answer the questions IF you don't know, just press Enter!
ZyRion Config Serial Number!
----------------------------
Last word about the ZYRIONn.CTL file, each CTL file has his unique Serial
number, IF this number is NOT okay, then ZyRion will tell you about it and
you'll need to re-setup ZyRion.
After the normal setup screen, you can change the default colors, well I'll
let you play with that, just return is the default color.
After this setup You are ready to USE, ZyRion. [UN] [RG] [EVAL]
EXIT STATUS
ZyRion exits with 0 status for successful transfers, or the value of the
X numeric parameter [ 1 ], if a file transfer failed, or if no files were
transferred. Many languages and "door" programs do not return this
information to the calling program. Some languages and "door" programs
freak out (hang) on certain non-zero exit values.
A batch file that calls ZyRion directly may be used to detect the ZyRion
exit status with the DOS "errorlevel" construct.
Remote Access
-------------
IF you want that ZyRion makes a "LOG" file put this in your autoexec.bat
file. "Special for Remote Access"
SET ZYRLOG=<DRIVE><PATH><LOG_FILENAME>
For Example
SET ZYRLOG=C:\RA\Z2RA.LOG or SET ZYRLOG=C:\DOS\COMM\ZYRION.LOG e.c
Next add ZyRion to RA using RACONFIG.
The "LOG" ZyRion creates looks like this :
R ARJVIEW.ARJ (FileSize 9707 Bytes) { Receivers "LOG" file }
S ARJVIEW.ARJ (FileSize 9707 Bytes) { Sender "LOG" file }
Besides that ZyRion will Exit with a Errorlevel 1 if BAD, and 0 for GOOD.
However IF used with Remote Access, and the carrier Drops, normal ZyRion
Will save to disk ALL Good data that what was received, and IF the user
calls again, Crash Recovery takes place.
I don't know "and have NOT tested" this under Remote Access, Please read
the RA-DOC in this case.
Remember ZyRion can ONLY recover a file if the data what was received is
still there, but that is logical, and you'll understand this.
Next here is the Snap Screen so as I have set it up in Remote Access :
══════════════════════════════════════════════════════════════╒════════════╕═══
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Msg areas │▒▒▒
▒╒══════════════════════════════════════════════════════ External protocol 1 ╕▒
▒│ │▒
▒│ Name ZyRion │▒
▒│ Key R │▒
▒│ Ext ctl file Yes │▒
▒│ Batch Yes │▒
▒│ Status Always available │▒
▒│ Log file D:\RABBS\ZYRION.LOG │▒
▒│ Control file SEND.CTL │▒
▒│ DL command line C:\LY130\ZYRION.EXE S -P*P -B*B @SEND.CTL │▒
▒│ UL command line C:\LY130\ZYRION.EXE R -P*P -B*B C:\OPUS\NEW\ │▒
▒│ DL ctl string │▒
▒│ UL ctl string │▒
▒│ DL log keyword S │▒
▒│ UL log keyword R │▒
▒│ Log name word 1 │▒
▒│ Log desc word 0 │▒
▒│ │▒
▒╘═══════════════════════════════════════════════════════════════════════════╛▒
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
───────────────────────────────────────────────────────────────────────────────
ZyRion can read normal SEND.CTL files "Path & Filenames" only but also the
Opus style Send CTL file.
NOTE >> PLEASE: Let me know IF you have problems.
FileDoor
--------
If you still have problems to install ZyRion as external protocol under
RA, it will work for sure with FileDoor.
Thanks Rob! and Reinier!
I still see that people have installed ZyRion under FileDoor BUT wrong
configured, FileDoor will say No File(s) Send or Received, or Both.
Therefore here the GOOD one, put this in your Filedoor.cfg file and it
will work!
Protocol 98 A U 10 0 ZyRion Batch
ErrorLevel C:\ly130\zyrion.exe R -P$1 -B$2 $U $M
Protocol 98 A D 10 0 ZyRion Batch
ErrorLevel C:\ly130\zyrion.exe S -P$1 -B$2 $3 $M
If ZyRion is Locked then use this >
Protocol 98 A U 10 0 ZyRion Batch
ErrorLevel C:\ly130\zyrion.exe R -P$1 -C$2 $U $M
Protocol 98 A D 10 0 ZyRion Batch
ErrorLevel C:\ly130\zyrion.exe S -P$1 -C$2 $3 $M
***********************************************************
WARNING
When running ZyRion under a multi tasking system such as DESQview, do not
allow two programs to access the same comm port at the same time. At
best, such actions will disrupt communications. At worst, your computer
will attempt to open a subdeep channel to the bottom of the sea.
Tell DESQview to use the SPECIFIC port number you are using, and not "Y"
to the question: "Uses serial Ports (Y, N, 1, 2)"
When running a comm program under DESQview or any related multitasking
executive, ZyRion must be called directly from the comm program, in the
same window. DO NOT open a separate window for ZYRION unless you were
about to power down the computer anyway.
***********************************************************
ZyRion FINISHED! exit code = 0 [ No Errors and so on ].
This is ZyRion's normal exit when at least one file has been transferred
and no unrecoverable errors have been detected. If an error such as a
failed file transfer had been detected, the exit code would be 1.
As the message implies, ZyRion has done all of its processing, and has
return the communications port and vector to its original value before
displaying this message. If the computer locks up after this message is
displayed, there's something wrong with the program that called ZyRion,
_NOT_ with ZyRion itself.
SLOW TRANSFERS
Some Beta Testers report slower than expected file transfers even when
few or no errors are reported. Some possible causes are:
If NO "CTS/RTS handshake" is used, throughput may suffer. (DFC is special)
And it may cause this problem.
Bad phone lines will silently slow MNP modems, sometimes without any
error indications. If the modems disconnect fairly often you should
suspect marginal phone line conditions that are being hidden by MNP
error correction.
One of the programs may have set a parameter or option that acts to slow
the transfer under certain conditions.
ZyRion Reference Rev Dec-25-91
IN CASE OF DIFFICULTY
LOCKUPS
Insufficient Memory
ZyRion complains when it detects insufficient memory to operate. When
calling ZyRion from another program, there may be ALMOST enough memory for
proper operation, but ZyRion locks up during a transfer or the calling
program freezes after ZyRion displays the "ZyRion Finished" message.
Sometimes there is a message about insufficient memory, sometimes just a
lockup and no message. To verify this problem, call CHKDSK from within
your comms program (not from DOS!) by defining it as an external
protocol. If you use an interface program (Hotkeyz, Prodoor, etc.), you
must call CHKDSK from that program, as those programs also reduce the
memory available to ZyRion.
CHKDSK should report at least 64k free memory. If less memory is
reported, reduce the size of the COMMS program's capture buffer, or
reboot the system with fewer/smaller device drivers and TSR programs.
Calling __ZyRion__ directly from the comms program instead of from an
interface also saves memory.
Cheap Internal Modems
Numerous trouble reports have been received lately caused by cheap
internal modems causing errors on ZYRION transfers but not XMODEM. A
similar problem was experienced in mid 91 during beta testing of
some 2400 bps modems. Perhaps defective LSI chips left over from those
days were cloned or recovered from the trash bin.
Brain Damaged UARTS
ProToSoFt (CR) has received reports of problems with buggy 8250 type
UART integrated circuits in Leading Edge modem boards, serial port
interfaces, and computers. The defective chip logic affects high
performance software. Replacing the buggy chip with a newer chip
(NS16550AN) corrects the problem.
The UM82450 chip in the Zoom 2400HC also appears to cause problems.
Zoom Telephonics advises that this problem is limited to their old
model. The old model is inentifiable by an external volume control.
You can identify an old chip by inspecting the serial interface board
for 8250 or UM82450 type devices. A service technician or hardware
hacker can help if you are not familiar with reading chip numbers.
The National Semiconductor NS16550AN is a pin compatible plug in
replacement for 8250 and 16450 serial chips. ProToSoFt's software
enables the FIFO buffer in the NS16550AN to prevents loss of data from
poorly written device drivers, TSR programs, etc.
We are also using the Goldstar GM82C550 chip with a 9025 date code.
This Goldstar chip is plug compatible with the National chips. No
problems have been discovered with this chip.
The NS16550AN has better electrical characteristics than the older UART
chips. 386 and fast 286 machines should use the NS16550AN for best
results. ProToSoFt (CR) Inc software has been written to allow time for
the older UART chips to operate. However, there is a limit to how much
the software can rearrange chip accesses without resorting to
performance robbing wait loops. Some other software is not as forgiving
of slow chips.
Be sure to ask for the NS16550AN. It is VITAL to get the National
Semiconductor "AFN" or "AN" chip. Other vendors' chips not mentioned
above won't do. Current Western Digital WD16C550 chips do not function
properly at low speeds.
As of this writing, the Goldstar GM82C550, National Semiconductor
NS16550AN and NS16550FAN are the only plug compatible chips that are
known to work.
The Hayes ESP board comes with two serial ports with NS16550A devices.
The ESP definitions for COM3 and COM4 agree with the industry standard
definitions used by International Communication Research [ ICR ].
Disk Caches
Cache programs often interfere with ZYRION transfers. In one instance,
replacing Microsoft's SMARTDRV.SYS with Multisoft's SUPERPCK.EXE helped.
Some cache programs can be turned on and off; try turning it off when
running ZyRion.
Switching to a National NS16550AN or NS16550AFN UART chip helps
tremendously, allowing transfers at 115200 bps instead of 9600 bps with
a standard 8250. Please refer to the subchapter on "Brain Damaged
UARTs".
ZyRion 2.45.1WB --- "Lets get started somewhere" ---
Command Line switches
R or S.......First parameter to tell ZyRion "Send or Receive".
-Px..........Second parameter to tell ZyRion the port number "COM1=1
So x will be 1 -P1 and so on.
-Bnnnnnn.....Third parameter "IF NOT LOCKED!" this will tell ZyRion
the real baudrate, So if you have a connection at 2400 bps
Then -Bnnnnnn will be -B2400
-Cnnnnnn.....Also Third parameter "IF LOCKED!" this will tell ZyRion
the connect rate, NOT the DTE rate, but the CONNECT XXXXX -
String from your high speed modem, thats this one!
For Example your DTE rate is constant 38400 Bits/Sec and
the remote connection is a CONNECT 9600 then -C need to be
-C9600 if the connection is a CONNECT 2400 then -C will be
-C2400 and so on.
Path/Files...The last series parameters are related to the Send or Receive
mode.
The Path is the directory where you want the files, in receive
mode, in Send mode it is the path to your files, ready to send
for Example if you want to send files from 3 directory's - -
then do this:
Zyrion S -p*p -b*b c:\dir1\*.arj c:\dir2\*.pas a:\dir3\*.txt
If you receiving files one inbound directory is needed, you -
can put that one in the Zyrionx.ctl file(s) or simple by put
it on thre command line, for example :
Zyrion R -p*p -b*b c:\myfiles\
All files will be received in the directory myfiles, also if a
connection was lost "Restart files" crash recovery!
If you receive files in all kind of directory's multi-node, be
sure to let them point to one directory, just in case so that
ZyRion can perform a Recovery easy, because IF ZyRion don't find
the "Restart Files" they will be marked as "NEW", and NOT as -
"RECOVER".
"."..........If no Path is suplied in the receive mode a "." will tell ZyRion
to put ALL files in the current directory.
For Example :
Zyrion R -p*p -b*b .
Locked.......If you have ZyRion in Locked mode, what means at a constant speed
or "DTE RATE", this is the constant "NOT CHANGED" speed between
your modem and your serial port, then you need to use the -Cnnnnnn
parameter NOT the -Bnnnnnn Parameter.
ZyRion will ignore the -Bnnnnnn parameter in the locked mode!
Please don't get confused with your fossil driver, If you have
your port locked with the Fossil "X00,BNU e.c" you still need to
tell ZyRion also to use a locked rate at a specified baudrate, - -
this can be 9600,14400,19200,38400 and so on.
After this your Modem will tell your communication package or BBS
software the CONNECT RATE, like Connected at 2400 baud, this is -
the connect rate, ZyRion will need this information also, for time
and transfer calculations "CPS rate e.c"....
Lets asume for a minute that the *c variable is your connect baud-
rate then you need to do this :
Zyrion S -p*p -c*c c:\dir1\*.arj c:\dir2\*.pas a:\dir3\*.txt
or ..
Zyrion R -p*p -c*c c:\myfiles\
or ..
Zyrion R -p*p -c*c .
Abarate......Just a nice name for Auto_BAud_RATE, to enable this option simple -
use -B0 instead of the baudrate, Please note: that this option - -
only works in a NOT locked mode!
for example :
Zyrion S -p*p -b0 c:\dir1\*.arj c:\dir2\*.pas a:\dir3\*.txt
or ..
Zyrion R -p*p -b0 c:\myfiles\
or ..
Zyrion R -p*p -b0 .
In this mode, ZyRion will read the current baudrate and will use
it!
ANTI_MTE....ZyRion will use BICHK see below also for scanning the data stream
before it passes the DFC<Tm> Engine, for MTE encrypted data files
the external engine is NOT ready yet, this Engine will be availble
so soon as I have talk this over and over with Victor Smith, author
of GII Virus Scan System!
CPS_BICHK....ZyRion starts with a low CPS rate, why?, because ZyRion checks all
data by resending Sync points, this will produce some overhead.
but since the new standard DFC, what is a Trade Mark of F.Lupschen
It will quick go up to a higher CPS rate, ZyRion has one goal and
that is NOT SPEED, but reliable data transfers, at a speed equal
or better then other protocols, most transfers are faster because
ZyRion works in a complete other way, therefore its a new designe
Engine, with more power and reliable transfers then I have - -
encountered, ZyRion uses Bidirectional transfers but NOT for data
in both directions, one direction is for the data stream "Flow" -
The other the reverse channel is for recovery and sync frames and
so on, therefore and only for this purpose, I did a BiCheck to -
give the users of ZyRion a 100% reliable file transfer protocol.
Not to play games, chat or whatsoever, that task is for multi -
taskers!
Fossil.......ZyRion does NOT use any Fossil driver, it has his own build in -
Serial I/O library also designed by Frans Lupschen.
This library is full calibrated on all internal routines of ZyRion
A fossil would fail in some cases to do this task, however The -
build in I/O Serial library will NOT conflict with a Fossil, so
there is NO need to turn your fossil off!
Setupn.......ZyRion can easy and fast make control files for up to 8 ports.
All complete separated, just type :
Zyrion setup1 for COM1
Zyrion setup2 for COM2 ...... And so on
Int SNP......Internal SNP number will fast -- Decrypted "Secure" to be sure -
the other end has NOT a hacked or same key "Improved" in this -
Version!
Sendbyte.....SendByte logic has also be improved and will be faster then in -
Version 2.42 and 2.43!
Ports........ZyRion ports and Fossil ports are not the same, a fossil uses -
for COM1 port 0, and ZyRion will use Port 1.
@Ctlfile.....The @ parameter will tell ZyRion to use a ASCII file list as -
send file, you can put so many files included paths as you want.
this will overide the DOS limit, for example :
Zyrion S -p*p -b*b @Send.ctl { Not Locked }
or
Zyrion S -p*p -c*c @Send.ctl { Locked }
CtlFormat....The format from this control file is simple, look at the examples
below.
Send1.ctl file
c:\in\games\cm3000-1.arj
c:\in\games\cm3000-2.arj
d:\icr\rel\zr244l1.arj
and so on ..
or
Send1.ctl file
cm3000-1.arj
cm3000-2.arj
zr244l1.arj
If no path is needed, in case you send these files from the above
paths, and so on ..
Auto_D/L.....Zyrion will send "senders site" a Autodownload sequence "ar...."
The "ar" are the first two sequences in the attn to indicate that
ZyRion has start in transmit mode.
Some Communications packages do support an additional "auto/DL"
sequence, related to the External protocol, "ar" need to be used
You may search futher in the Header string what Zyrion sends, see
for more info about this under "TX-Header".
ExitCode.....ZyRion will Exit with a errorlevel 0, if all data was transfered
without "fatal errors" or "Interactions", otherwise ZyRion will
Exit with a errorlevel 1, Use this in FileDoor<Tm>, or other -
Protocol interfaced programs.
TIMESYNC.....ZyRion starts with a low CPS rate, why?, because ZyRion checks all
data by resending Sync points, this will produce some overhead.
I have Added in this version a TIME SYNC Frame, so soon as both
Zyrion's are in header state, both timers from the receiver and -
sender are set to "Zero" this will be the case each time a new -
file will be transfered, the result from this extra frame is a -
better CPS rate and stable, besites that the CPS rate from the -
sender and receiver are the same!
The TSYNC frame is more then just a time reset, it will also - -
Equalize the data stream, it will force the abarated driver to
use more or less buffer space, this to keep the data flow in a
constant move.
Also the connect rate NOT the DTE rate if locked will be Equalized
if one end is at 460 CPS and the other end at 440 CPS, then we -
have two not equal connect rates 460 X 10 = 4600 Bps and on the -
other end we have 440 X 10 = 4400 BPS, at this point the Equalizer
routine will try to get both sites at the same transfer rate, in
this example Zyrion will try to get both sites at 450 X 10 BPS!
This by sending the TSYNC frame over the CPS_BICHK, in short the
overhead will be less then before.
NOTE :: Time Sync Equalize will NOT work with older versions they
are still compatible but this new frame will then be -
skipped!
Only gamma 244 - 2 will use it, and have a better CPS
rate ... and so on.
TX-HEADER....This is the header from the sender and it can be used to trigger
an autodownload.
ATTN-ZINFS-ZSYNCS-SPACE-VERSION-SPACE-USERNAME-SPACE-ZSEPEND->
The header + user info looks complete like this below :
Z1≥ 244.1Σb Frans Lupschen ≡%%Z0000000000000000
1 - ATTN = Z1
2 - ZINFS = (20)
3 - ZSYNCS = ≥ (242)
4 - SPACE = " " (32)
VERSION = "Zyrion Version number"
USERNAME = "usersname"
5 - ZSEPEND = ≡ (240)
6 - ZZPDD = % (37)
7 - HEXMARK = Z (90)
8 - ZCAN = (24)
BININIT = 0000000000000000
ZREND = N/A For users
ZSEP = N/A For users
BICHK = N/A For users
TIMESYNC = N/A For users
If you search only for 1 and 2 would be good, but 1,2,3 is better
there is NO need to search for the other info since version and -
special username are NOT constant.
However you can also search for the complete pattern 1,2,3,4,5,6,
7,8 or for 5,6,7,8, that up to you.
ZCR BUG Fixed
-------------
Small but nesty that was the bug in ZCR, ZCR did NOT close the
ZYRIONx.CTL file at the time a user/tester used the edit function
the result was that the editor defined in ZCR.CTL could not save
the file because the file was not closed by ZCR "FIXED"!
Sample Send Control File Format:
C:\DRIVERS\MPT110.ZIP
C:\DRIVERS\TMOD610.ARJ
C:\DRIVERS\ZMOD*.*
^^^^^^^^
|
Please notice, that ZyRion will NOT do batch in this case, it will search
for the first match, so a file that starts with ZMOD*.*, if you want to do
multiple batch transfers then use :
ZYRION S -P2 -B0 C:\HPM\*.ZIP D:\GAMES\GLO*.* A:\*.SYS B:\DOS\CHK*.* e.g
Again remember that IF ZyRion is NOT registered the above samples will work
BUT ZyRion will only send one file.
There are DEMO key's "good for 30 days" you can obtain a key here from
2:284/304 or 2:285/802 or in the states Marlin Lee England.
LAST NEWS
---------
ZyRion Yield now 1876 CPS at High Speed, low speed xfers are equal, but stable
Thats because the Async lib. is at full speed, no debug routines enabled in -
that sector anymore.
Small bug fixed in the (New File) (Recover File) e.c .
ZyRion<Tm> file transfer recovery and advanced file management security and -
priority data are dedicated to :
XModem, YModem, Sealink, ZModem, ZedZap, BiSync!
New in header TiSync data headings, TiSync data headings vary with -
applications, but typical information contained in a heading is as -
follows:
o Identification of originating device
o Identification of receiving device
o Priority of data
o Data security class
o Destination routing for data ( special environment )
o DFC control or information nature of data
TiSync/DFC/ADLC/HDLC
--------------------
TiSync/DFC is close related to ADLC From IBM, but more to HDLC, HDLC means
High Level Data Link Control normal for Syncronous data transfer protocols
The TiSync has the same basic idea and is normal NOT used by hobbyist -
because of their initial cost, but since HDLC is world standards for -
business communications.
ZyRion therefore is NOT only for the BBS marked, but can also be used in a
business communications environment, since it has the info stored in the -
header for separated work stations ( remote networks ).
IBM uses BiSync, but since this is copyrighted I have worked out a complete
own idea, and the basic concept was and is still DFC.
DFC works like a serial stream of binary numbers, and is therefore more
reliable then a block CRC data patern.
ZyRion will build a matrix, and that will be checked by LRC and VRC to get
the result.
LRC means longitudinal redundancy checking, and VRC means vertical redundancy
checking, VRC will NOT check the ODD parity but I use it to send a bidirec -
tional frame segment if needed to check the accuracy of the received data.
Exitinfo will not longer be displayed to your screen, but only to
the ExitCode.inf file, Purpose if there is a error/ bug or whatsover
send me that file.
Conflict routine now stable (Fixed)
ZCR has been changed "Internal" and some small bugs fixed.
Also you can use ZCR <PORT>, to view the zyrion<port>.ctl file direct, nice
if you have only one port, for example if you use com4 use "ZCR 4" thats all
ZCR <Cr> will force ZCR.EXE to search for ctl files!
ZyRion Async Routine has been changed, internal rev code 3.00ß1
Let me know if you got comm conflicts with other software!!
ZyRion conflict routine has been improved, you'll get a nice message and
other stuff if both sites have/use the same key! { Check it out!! }
for people who want ZyRion's Base Address, and IRQ for each port here a list
(*-------------------------------------------------------------------------*)
(* Base Address for each Port *)
(*-------------------------------------------------------------------------*)
CONST
BASE1 : WORD = $3F8;
BASE2 : WORD = $2F8;
BASE3 : WORD = $3E8;
BASE4 : WORD = $2E8;
BASE5 : WORD = $2B8;
BASE6 : WORD = $2B8;
BASE7 : WORD = $2F8;
BASE8 : WORD = $278;
(*-------------------------------------------------------------------------*)
(* IRQ Lines are defined here *)
(*-------------------------------------------------------------------------*)
IRQ1 : WORD = 4;
IRQ2 : WORD = 3;
IRQ3 : WORD = 4;
IRQ4 : WORD = 3;
IRQ5 : WORD = 3;
IRQ6 : WORD = 2;
IRQ7 : WORD = 2;
IRQ8 : WORD = 2;
(* End Define Base AND Irq lines *)
Please be aware that, in this version the Selfdestruct mode is enabled!
Once you use a key from another Sysop for example and you want to test with
him, you'll get this message on your screen, after that ZyRion will NOT run
until the file for it has been removed, give a look at it below :
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
▒ ▒
▒ WHAT This system VIOLATED OUR SOFTWARE LICENSE AGREEMENT by ▒
▒ IS using SAME LICENSE KEY NUMBER on two or more systems. ▒
▒ THIS? We know this because your ZyRion site has connected ▒
▒ with another system with the same key number. WE HOPE ▒
▒ THAT YOU DO NOT INTEND TO USE OUR SOFTWARE ILLEGALLY! ▒
▒ ▒
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
▒ ▒
▒ Whether this communication occurred knowingly or without your ▒
▒ knowledge, THIS IS AN OBVIOUS VIOLATION OF THE SOFTWARE COPY- ▒
▒ RIGHT. We will absolutely not allow this to happen all the ▒
▒ time... If this was done accidently or it occured as part of ▒
▒ "limited diagnostic testing," please accept our apologies for ▒
▒ the inconvience this may have caused you. ▒
▒ Simply delete VIOLATED.LOG to restore operations and the problem ▒
▒ will go away permanently unless there are more violations in the ▒
▒ future. ▒
▒ ▒
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
▒ ▒
▒ Please call ICR Holland or a Distribution site for customer - ▒
▒ support if you are confused! [ +31-45-256961 ] ▒
▒ ▒
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
▒ ▒
▒ VIOLATED It did not happen this time, but if you keep violating ▒
▒ LICENSE the authors copyright, your system might destroy this ▒
▒ "DETROY ZyRion release, included with your ZyRion.Key! ▒
▒ MODE!" Violation "Destroy Mode" occur quite infrequently, ▒
▒ but could happen anytime if the violations continue. ▒
▒ For your UNREGISTERED copy! ▒
▒ The current "odds of notification" are 1 in 40.6! ▒
▒ ▒
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
After this message on both ends the DTR will be lowered and the connection
has been terminated by ZyRion, HINT : Got yourself a good key.
Special Thanks to :
Rob Van Hoeven Rob Van Der Hoeven Reinier De Groot
John Lots Marlin Lee England Jan Janmaat
Jaap Huizinga Dennis Hammerstein Rodolfo Vardelli
Truus Pisano Cindy England Aad Vlasblom
Jack Linssen Herman Ter Braake Nick Klein
Dick Hoogendijk